Design Round 8 · Deliverable 4 · Kiduna Express · kiduna.express · Chrome · July 13, 2026
Express — the Field meets the open web
Express does not put the Field on top of the web; it lets the web tell the truth in the Field's vocabulary. Registered and unregistered rendered honestly — a stranger, not a threat (4a); everything done through Express happening, by default, inside Kinship Duna (4b); registering resources and domains with an Organization (4c); and your ally acting across pages under your authority (4d).
4a
A page, honestly — registered lights up; unregistered stays what it always was
The page keeps its own skin. Express never repaints the web espresso. Registered things gain one quiet chip stating what the registration traces to — member, Organization, Institution — every claim walkable to its Record. Unregistered things get no mark at all unless you ask; asking gets the plain sentence, never a warning triangle.
the rendering law
Registered / unregistered is for resources. Sites, pages, accounts, artifacts. Registration is a fact with a trace, never a virtue.
Trusted / untrusted is for relationships. Express never renders a site as "trusted" — the axes never blur (law).
No identity-sameness without registered proof. A matching name on two platforms renders as nothing; a registered link renders as a scoped, dated account link.
Unregistered is the web's normal. Most of the internet, most of it good. The chip's absence is not a judgment.
4b
Everything you do here happens somewhere — Kinship Duna, by default
The container chip lives in the toolbar. "in Kinship Duna" — because every action any member or agent takes is taken inside an Organization, as a member of it, and open-web browsing not claimed by a specific one belongs to the genesis Organization by default.
Acting for an Organization is one sentence. "Do this as The Ceremony Machine" — the chip changes, the register changes, and everything that follows lands in that Organization's Records. A drift, not a login.
The chip is a statement of accountability, not surveillance. Express records the acts your ally takes and the resources you register — not your reading. Browsing history stays the browser's; the Field keeps only what became an act.
The chip answers the web's oldest missing question — on whose behalf is this happening? — with a name that can be held to account.
4c
Registering a resource — the web object gains a Record
Domain proof precedes the hold — the ally walks the DNS verification and states what was proven. From the moment of registration, every Express user who lands on the domain sees the chip and can walk it to this Record.
what can be registered from Express
Domains and pages — to an Organization, with a proof step.
Your own social accounts — bound to your registry identity after login through Studio; rendered as scoped, dated links.
Artifacts — a post, a paper, a repo release — cited into a Project's materials, provenance kept.
Registration of an Organization itself, KYB for Institutions, and anything touching money stay on the web's account surfaces — kidunaverse.com and kiduna.cash.
4d
Your ally across pages — under your authority, leaving receipts
The channel law holds on the open web. Member → ally → ally → member, even when the meeting place is Bluesky. Your ally filters what comes back per your preferences; only you — the Source — direct it. Posting to your own registered account is a granted act with a receipt; acting on another member's post routes through their ally, never around it.
Express's sentence, R8: the web stays the web — what changes is that things can finally say who they are, and your ally can finally act where you already live.
What Express refuses: repainting pages · blocking unregistered content · any "safety score" for sites · acting without a receipt · money (kiduna.cash is one click away, and stays there).